Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1393

reference
665-tree-1
name
1393
tree-preservation-order

undefined

665-tpo-1
uprn
address-text
point
POINT (-1.022796 50.880813)
geometry
MULTIPOLYGON (((-1.022711 50.880804,-1.022715 50.880821,-1.022727 50.880836,-1.022745 50.880848,-1.022769 50.880856,-1.022795 50.880859,-1.022821 50.880857,-1.022845 50.880849,-1.022865 50.880837,-1.022877 50.880822,-1.022881 50.880806,-1.022878 50.880789,-1.022866 50.880774,-1.022847 50.880762,-1.022824 50.880754,-1.022797 50.880751,-1.022771 50.880753,-1.022747 50.880761,-1.022728 50.880773,-1.022715 50.880788,-1.022711 50.880804)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL